-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/7.0] Fix Settings_MaxHeaderListSize_Server #46251
Conversation
Hi @wtgodbe. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Hmm, looks like this fix is incomplete. Gonna see if I missed something
|
I don't see anything in the file history in |
Can you check the response status code (the prior condition)? Are you sure you have the runtime change available in this branch? |
Which one do you mean? I don't see us checking that in the test
I couldn't find which runtime change caused the original failure, it wasn't linked in the PR - is it this one? dotnet/runtime#79281 - that is in 7.0. And we are currently seeing the same test failure as described in #45811 in 7.0 |
Oh, I know what's happening - internal dependency flow. That change probably hasn't flowed to the public branch yet. I bet this'll work after the internal -> public merge. |
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
/azp run |
Commenter does not have sufficient privileges for PR 46251 in repo dotnet/aspnetcore |
/azp run |
Azure Pipelines successfully started running 3 pipeline(s). |
I suspect this won't work until next Tuesday (internal -> public merge that'll bring in the dependency flow commits from Feb). If that messes with the timing we could just move this PR to the internal repo - @mmitche what's your preference? |
Merged commits from here into #46646. Suggest closing. |
Pull request was closed
Ports test fix for #45811 which is already in
main
. Can wait for March.